- Update define step to create job.yml in .deepwork/jobs/[job_name]/ instead of deepwork/[job_name]/
- Update implement step to verify job.yml location instead of copying from work directory
- Update job.yml quality criteria to check correct path
- Update README.md to use correct command names (deepwork_jobs.define, deepwork_jobs.refine)
- Sync changes to all installed files and generated commands

Creates a 4-step workflow for adding new AI platforms to DeepWork:
- research: Capture CLI config and hooks documentation
- add_capabilities: Update schema and adapters with new hooks
- implement: Create adapter, templates, tests (100% coverage)
- verify: Ensure installation works correctly

Each step includes quality validation stop hooks.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Document Gemini CLI configuration and hooks system:
- cli_configuration.md: TOML command format, discovery, namespacing
- hooks_system.md: No command-level hooks (only global hooks in settings.json)

Key findings:
- Commands stored in .gemini/commands/ (TOML format)
- No hooks available in slash command definitions
- Global hooks exist but cannot be configured per-command

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

No new hooks added to schema - Gemini CLI does not support command-level hooks.

Analysis findings:
- Gemini CLI TOML command files only support 'prompt' and 'description' fields
- Global hooks exist in settings.json but are NOT per-command
- All existing DeepWork hooks (after_agent, before_tool, before_prompt) already
  cover the generic patterns; Gemini just won't support them

Added documentation block in adapters.py explaining hook support by platform.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add full platform support for Gemini CLI:

Adapter (src/deepwork/core/adapters.py):
- GeminiAdapter class with TOML command format
- Subdirectory-based namespacing (job_name/step_id.toml -> /job_name:step_id)
- Empty hook_name_mapping (Gemini has no command-level hooks)
- sync_hooks returns 0 (no-op since hooks are global-only)

Template (src/deepwork/templates/gemini/command-job-step.toml.jinja):
- TOML format with description and prompt fields
- Colon namespacing for command references
- Quality criteria embedded in prompt (since no stop_hooks)

Tests (tests/unit/test_adapters.py):
- 18 new tests for GeminiAdapter
- All adapter tests pass (36 total)
- Full coverage of new GeminiAdapter code

README.md:
- Added Supported Platforms table
- Gemini CLI installation instructions
- Platform-specific notes about hooks and TOML format
- Updated directory structure examples

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Verified Gemini CLI platform integration:
- deepwork install --platform gemini completes successfully
- All 8 TOML command files generated correctly
- Proper directory structure with subdirectory namespacing
- Cross-platform compatibility confirmed (Claude still works)
- Both platforms in .deepwork/config.yml

Generated files:
- .gemini/commands/deepwork_jobs/*.toml (3 files)
- .gemini/commands/deepwork_policy/define.toml
- .gemini/commands/add_platform/*.toml (4 files)

Verification report: deepwork/add_platform/verification_complete.md

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>